Add Hover to TabItem #28357

wildan-m · 2023-09-28T01:28:58Z

@Ollyws, @MariaHCD, @garrettmknight

Details

Add tab item styling when hovered

Fixed Issues

$ #26648
PROPOSAL: #26648 (comment)

Tests

Web / Desktop

Click FAB
Choose Request Money
Select Scan tab as the initial tab
Hover the mouse to Manual tab
Verify that Manual tab background color is equal to themeColors.highlightBG / darkHighlightBackground / #07271F
Verify that the icon and label color are the same as with the active tab (Scan tab)
Click Manual tab
Hover the mouse to Scan tab
Verify that Scan tab background color is equal to themeColors.highlightBG / darkHighlightBackground / #07271F
Verify that the icon and label color are the same as with the active tab (Manual tab)

Native / Mobile Web

Click FAB
Choose Request Money
Select Scan tab as the initial tab
Select Manual tab
Verify that there is no error

Verify that no errors appear in the JS console

Offline tests

Web / Desktop

Click FAB
Choose Request Money
Select Scan tab as the initial tab
Hover the mouse to Manual tab
Verify that Manual tab background color is equal to themeColors.highlightBG / darkHighlightBackground / #07271F
Verify that the icon and label color are the same as with the active tab (Scan tab)
Click Manual tab
Hover the mouse to Scan tab
Verify that Scan tab background color is equal to themeColors.highlightBG / darkHighlightBackground / #07271F
Verify that the icon and label color are the same as with the active tab (Manual tab)

Native / Mobile Web

Click FAB
Choose Request Money
Select Scan tab as the initial tab
Select Manual tab
Verify that there is no error

QA Steps

Web / Desktop

Click FAB
Choose Request Money
Select Scan tab as the initial tab
Hover the mouse to Manual tab
Verify that Manual tab background color is equal to themeColors.highlightBG / darkHighlightBackground / #07271F
Verify that the icon and label color are the same as with the active tab (Scan tab)
Click Manual tab
Hover the mouse to Scan tab
Verify that Scan tab background color is equal to themeColors.highlightBG / darkHighlightBackground / #07271F
Verify that the icon and label color are the same as with the active tab (Manual tab)

Native / Mobile Web

Click FAB
Choose Request Money
Select Scan tab as the initial tab
Select Manual tab
Verify that there is no error

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Web

Recording.79.mp4

Mobile Web - Chrome

Recording.81.mp4

Mobile Web - Safari

Recording.83.mp4

Desktop

Recording.84.mp4

iOS

Recording.82.mp4

Android

Recording.80.mp4

…x/26648-3-tab-hover

…dan-m/App into wildan/fix/26648-3-tab-hover

…x/26648-3-tab-hover

…dan-m/App into wildan/fix/26648-3-tab-hover

…x/26648-3-tab-hover

…dan-m/App into wildan/fix/26648-3-tab-hover

…x/26648-3-tab-hover

…dan-m/App into wildan/fix/26648-3-tab-hover

melvin-bot · 2023-09-28T01:29:02Z

@Ollyws Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

src/components/TabSelector/TabSelectorItem.js

Ollyws · 2023-09-28T17:45:47Z

src/components/TabSelector/TabSelector.js

@@ -82,7 +82,7 @@ const getBackgroundColor = (position, routesLength, tabIndex) => {

 function TabSelector({state, navigation, onTabPress, position}) {
    const {translate} = useLocalize();
-
+    const hoverBackgroundColor = themeColors.highlightBG;


Why are we defining this here and passing it as a prop rather than just passing the value inside TabSelectorItem?

Why are we defining this here and passing it as a prop rather than just passing the value inside TabSelectorItem?

I'm trying to make it consistent with how backgroundColor passed, also it can be a tiny feature in case we need to customize the tabitem hover color.

if that is not required we can directly use styles.highlightBG in the tabitem inner animated.view

@Ollyws , sorry I misunderstood your question, yes, we can simplify it without declaring a variable. it just updated.

Ollyws · 2023-09-28T20:25:23Z

@wildan-m Just wondering, did you do much testing with your original solution? Were there any performance drawbacks? Because it does seem a bit tidier to just have the Animated.View with the background and non-Animated pressable.

wildan-m · 2023-09-28T22:17:34Z

@Ollyws Yes I did.

How do I test it? I didn't involve hoverable changes in this test, just made changes in the AnimatedPressableWithFeedback.

This is three attempts profiling result to move the tab from Scan to Distance

PressableWithFeedback + Animated.View	AnimatedPressableWithFeedback

Ollyws · 2023-09-29T00:34:46Z

@wildan-m Ahh thanks, nice. Does this give a performance increase over using a hoverable?

wildan-m · 2023-10-06T22:31:00Z

@Ollyws that's weird, isn't it?

Even when we pass the hovered param to tabicon/label, the issue is occurred (Alternative 2)

For me, the only working solution that resolves all of these issues is this one: (don't forget to import StyleSheet from RN)

       <AnimatedPressableWithFeedback
            accessibilityLabel={title}
            style={[styles.tabSelectorButton, { backgroundColor }]}
            wrapperStyle={[styles.flex1]}
            onPress={onPress}
        >
            {({ hovered }) => (
                <View
                    style={[styles.tabSelectorButton, StyleSheet.absoluteFill, styles.tabBackground(hovered, isFocused)]}
                >
                    <TabIcon
                        icon={icon}
                        activeOpacity={styles.tabOpacity(hovered, isFocused, activeOpacity, inactiveOpacity)}
                        inactiveOpacity={styles.tabOpacity(hovered, isFocused, inactiveOpacity, activeOpacity)}
                    />
                    <TabLabel
                        title={title}
                        activeOpacity={styles.tabOpacity(hovered, isFocused, activeOpacity, inactiveOpacity)}
                        inactiveOpacity={styles.tabOpacity(hovered, isFocused, inactiveOpacity, activeOpacity)}
                    />
                </View>
            )}
        </AnimatedPressableWithFeedback>

styles tabBackground:

    tabBackground: (hovered, isFocused) => ({
        backgroundColor: hovered && !isFocused ? theme.highlightBG : undefined,
    }),

using Hoverable mixed with animated components might skip important render. are we okay with using the above change instead?

Ollyws · 2023-10-06T23:21:06Z

@wildan-m Yeah go ahead, thanks.

wildan-m · 2023-10-06T23:33:31Z

@Ollyws updated

Ollyws · 2023-10-07T11:22:11Z

@wildan-m Great, that seems to fix the issue.
If you could just apply these changes to tidy things up a bit then we should be good to go, thanks!

diff --git a/src/components/TabSelector/TabSelectorItem.js b/src/components/TabSelector/TabSelectorItem.js
index 168a783ad6..6611b8acf9 100644
--- a/src/components/TabSelector/TabSelectorItem.js
+++ b/src/components/TabSelector/TabSelectorItem.js
@@ -1,4 +1,4 @@
-import {Animated, View, StyleSheet} from 'react-native';
+import {Animated, StyleSheet} from 'react-native';
 import React from 'react';
 import PropTypes from 'prop-types';
 import styles from '../../styles/styles';
@@ -42,18 +42,16 @@ const defaultProps = {
     isFocused: false,
 };
 
-const AnimatedPressableWithFeedback = Animated.createAnimatedComponent(PressableWithFeedback);
-
 function TabSelectorItem({icon, title, onPress, backgroundColor, activeOpacity, inactiveOpacity, isFocused}) {
     return (
-        <AnimatedPressableWithFeedback
+        <PressableWithFeedback
             accessibilityLabel={title}
-            style={[styles.tabSelectorButton, {backgroundColor}]}
+            style={[styles.tabSelectorButton]}
             wrapperStyle={[styles.flex1]}
             onPress={onPress}
         >
             {({hovered}) => (
-                <View style={[styles.tabSelectorButton, StyleSheet.absoluteFill, styles.tabBackground(hovered, isFocused, undefined)]}>
+                <Animated.View style={[styles.tabSelectorButton, StyleSheet.absoluteFill, styles.tabBackground(hovered, isFocused, backgroundColor)]}>
                     <TabIcon
                         icon={icon}
                         activeOpacity={styles.tabOpacity(hovered, isFocused, activeOpacity, inactiveOpacity)}
@@ -64,9 +62,9 @@ function TabSelectorItem({icon, title, onPress, backgroundColor, activeOpacity,
                         activeOpacity={styles.tabOpacity(hovered, isFocused, activeOpacity, inactiveOpacity)}
                         inactiveOpacity={styles.tabOpacity(hovered, isFocused, inactiveOpacity, activeOpacity)}
                     />
-                </View>
+                </Animated.View>
             )}
-        </AnimatedPressableWithFeedback>
+        </PressableWithFeedback>
     );
 }
 
diff --git a/src/styles/styles.js b/src/styles/styles.js
index 81b3b139dc..418d76b67f 100644
--- a/src/styles/styles.js
+++ b/src/styles/styles.js
@@ -3450,8 +3450,8 @@ const styles = (theme) => ({
         color: isSelected ? theme.textLight : theme.textSupporting,
     }),
 
-    tabBackground: (hovered, isFocused) => ({
-        backgroundColor: hovered && !isFocused ? theme.highlightBG : undefined,
+    tabBackground: (hovered, isFocused, background) => ({
+        backgroundColor: hovered && !isFocused ? theme.highlightBG : background,
     }),
 
     tabOpacity: (hovered, isFocused, activeOpacityValue, inactiveOpacityValue) => (hovered && !isFocused ? inactiveOpacityValue : activeOpacityValue),

Diff

wildan-m · 2023-10-07T12:31:53Z

@Ollyws based on this test. Our recent changes are slightly better in terms of performance. Your proposed changes are option 2. Are you sure to apply it?

Ollyws · 2023-10-07T12:50:46Z

@wildan-m Yeah that's just a miniscule bump to render time, I don't think it's reflective of the animation performance and tidy code is worth it.

…x/26648-3-tab-hover

wildan-m · 2023-10-07T13:11:50Z

@Ollyws sure, change has been applied

Ollyws · 2023-10-08T10:08:13Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android / native
- Android / Chrome
- iOS / native
- iOS / Safari
- MacOS / Chrome / Safari
- MacOS / Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

01_MacOS_Chrome.mp4

Mobile Web - Chrome

02_Android_Chrome.mp4

Mobile Web - Safari

03_iOS_Safari.mp4

Desktop

04_MacOS_Desktop.mp4

iOS

05_iOS_Native.mp4

Android

06_Android_Native.mp4

Ollyws

LGTM.
Thanks for all the changes!

OSBotify · 2023-10-09T07:04:22Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2023-10-09T23:01:31Z

🚀 Deployed to staging by https://github.com/MariaHCD in version: 1.3.80-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2023-10-11T04:41:47Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.80-3 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅

OSBotify · 2023-10-11T05:10:41Z

🚀 Deployed to staging by https://github.com/MariaHCD in version: 1.3.81-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2023-10-13T21:59:47Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.83-11 🚀

platform	result
🤖 android 🤖	skipped 🚫
🖥 desktop 🖥	skipped 🚫
🍎 iOS 🍎	skipped 🚫
🕸 web 🕸	skipped 🚫

OSBotify · 2023-10-13T22:11:50Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.83-11 🚀

platform	result
🤖 android 🤖	skipped 🚫
🖥 desktop 🖥	skipped 🚫
🍎 iOS 🍎	skipped 🚫
🕸 web 🕸	skipped 🚫

OSBotify · 2023-10-13T22:28:04Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.83-11 🚀

platform	result
🤖 android 🤖	skipped 🚫
🖥 desktop 🖥	skipped 🚫
🍎 iOS 🍎	skipped 🚫
🕸 web 🕸	skipped 🚫

OSBotify · 2023-10-13T23:03:28Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.83-11 🚀

platform	result
🤖 android 🤖	failure ❌
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅

OSBotify · 2023-10-16T21:15:08Z

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.84-10 🚀

platform	result
🤖 android 🤖	skipped 🚫
🖥 desktop 🖥	skipped 🚫
🍎 iOS 🍎	skipped 🚫
🕸 web 🕸	skipped 🚫

OSBotify · 2023-10-16T21:51:28Z

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.84-10 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅

rayane-djouah · 2024-08-27T00:36:06Z

FYI, This PR caused #47381 you can a find RCA in this proposal: #47381 (comment)

wildan-m added 17 commits September 21, 2023 16:59

Separate pressable with animated.view, add hover color to tabitem

1cf2613

Merge branch 'main' of https://github.com/wildan-m/App into wildan/fi…

9810019

…x/26648-3-tab-hover

make tab label always strong

e3b8121

prettier and lint

6a4c887

Merge branch 'main' of https://github.com/wildan-m/App into wildan/fi…

c4d0a93

…x/26648-3-tab-hover

Merge branch 'main' of https://github.com/wildan-m/App into wildan/fi…

f81b3d5

…x/26648-3-tab-hover

Merge branch 'wildan/fix/26648-3-tab-hover' of https://github.com/wil…

52091e8

…dan-m/App into wildan/fix/26648-3-tab-hover

Merge branch 'main' of https://github.com/wildan-m/App into wildan/fi…

42265f0

…x/26648-3-tab-hover

Merge branch 'wildan/fix/26648-3-tab-hover' of https://github.com/wil…

a672fc0

…dan-m/App into wildan/fix/26648-3-tab-hover

Keep AnimatedPressableWithFeedback for optimum performance

ad0eb57

Merge branch 'main' of https://github.com/wildan-m/App into wildan/fi…

67842c1

…x/26648-3-tab-hover

Merge branch 'wildan/fix/26648-3-tab-hover' of https://github.com/wil…

edb3947

…dan-m/App into wildan/fix/26648-3-tab-hover

change to undefined instead of empty object

919c15d

Merge branch 'main' of https://github.com/wildan-m/App into wildan/fi…

477f181

…x/26648-3-tab-hover

Merge branch 'wildan/fix/26648-3-tab-hover' of https://github.com/wil…

9b7edfb

…dan-m/App into wildan/fix/26648-3-tab-hover

run prettier

395d6d8

remove unnecessary comment

941e1ca

wildan-m requested a review from a team as a code owner September 28, 2023 01:28

melvin-bot bot requested review from Ollyws and removed request for a team September 28, 2023 01:29

wildan-m mentioned this pull request Sep 28, 2023

[HOLD for payment 2023-10-18] [$1000] Web - Request money - No hover indicator for top tab options #26648

Closed

6 tasks

wildan-m changed the title ~~Wildan/fix/26648 Add tab hover~~ Add Hover to TabItem Sep 28, 2023

Ollyws reviewed Sep 28, 2023

View reviewed changes

src/components/TabSelector/TabSelectorItem.js Outdated Show resolved Hide resolved

change view to animated.view

5373a25

Ollyws reviewed Sep 28, 2023

View reviewed changes

remove unnecessary variable

f2dd997

Resolve issue hover not working after pressing back from another screen

00945f4

wildan-m added 2 commits October 7, 2023 19:56

Merge branch 'main' of https://github.com/wildan-m/App into wildan/fi…

b783633

…x/26648-3-tab-hover

tidy up code

bab483b

run prettier

e2f3650

Ollyws approved these changes Oct 8, 2023

View reviewed changes

melvin-bot bot requested a review from MariaHCD October 8, 2023 10:10

MariaHCD approved these changes Oct 9, 2023

View reviewed changes

MariaHCD merged commit 7c7fa65 into Expensify:main Oct 9, 2023
14 checks passed

OSBotify mentioned this pull request Oct 9, 2023

Deploy Checklist: New Expensify 2023-10-09 #29131

Closed

64 tasks

OSBotify mentioned this pull request Oct 11, 2023

Deploy Checklist: New Expensify 2023-10-11 #29252

Closed

rayane-djouah mentioned this pull request Aug 27, 2024

[$250] Blue "Pill" Highlight is very light when using Tab/Shift #47381

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add Hover to TabItem #28357

Add Hover to TabItem #28357

wildan-m commented Sep 28, 2023

melvin-bot bot commented Sep 28, 2023

Ollyws Sep 28, 2023

wildan-m Sep 28, 2023

wildan-m Sep 28, 2023

wildan-m Sep 28, 2023

Ollyws commented Sep 28, 2023 •

edited

Loading

wildan-m commented Sep 28, 2023

Ollyws commented Sep 29, 2023

wildan-m commented Oct 6, 2023 •

edited

Loading

Ollyws commented Oct 6, 2023

wildan-m commented Oct 6, 2023

Ollyws commented Oct 7, 2023

wildan-m commented Oct 7, 2023

Ollyws commented Oct 7, 2023

wildan-m commented Oct 7, 2023

Ollyws commented Oct 8, 2023

Ollyws left a comment

OSBotify commented Oct 9, 2023

OSBotify commented Oct 9, 2023

OSBotify commented Oct 11, 2023

OSBotify commented Oct 11, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 16, 2023

OSBotify commented Oct 16, 2023

rayane-djouah commented Aug 27, 2024

Add Hover to TabItem #28357

Add Hover to TabItem #28357

Conversation

wildan-m commented Sep 28, 2023

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Sep 28, 2023

Ollyws Sep 28, 2023

Choose a reason for hiding this comment

wildan-m Sep 28, 2023

Choose a reason for hiding this comment

wildan-m Sep 28, 2023

Choose a reason for hiding this comment

wildan-m Sep 28, 2023

Choose a reason for hiding this comment

Ollyws commented Sep 28, 2023 • edited Loading

wildan-m commented Sep 28, 2023

Ollyws commented Sep 29, 2023

wildan-m commented Oct 6, 2023 • edited Loading

Ollyws commented Oct 6, 2023

wildan-m commented Oct 6, 2023

Ollyws commented Oct 7, 2023

wildan-m commented Oct 7, 2023

Ollyws commented Oct 7, 2023

wildan-m commented Oct 7, 2023

Ollyws commented Oct 8, 2023

Reviewer Checklist

Screenshots/Videos

Ollyws left a comment

Choose a reason for hiding this comment

OSBotify commented Oct 9, 2023

OSBotify commented Oct 9, 2023

OSBotify commented Oct 11, 2023

OSBotify commented Oct 11, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 16, 2023

OSBotify commented Oct 16, 2023

rayane-djouah commented Aug 27, 2024

Ollyws commented Sep 28, 2023 •

edited

Loading

wildan-m commented Oct 6, 2023 •

edited

Loading